Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[v4.9] Bump Buildah to v1.33.11, fix CVE-2024-9676 #24375

Open
wants to merge 1 commit into
base: v4.9
Choose a base branch
from

Conversation

TomSweeneyRedHat
Copy link
Member

Fixes CVE-2024-9676 in the Podman v4.9 release branch.

Also addresses: CVE-2024-9675, CVE-2024-9407, and CVE-2024-9341

[NO NEW TESTS NEEDED]

Does this PR introduce a user-facing change?

None

Fixes CVE-2024-9676 in the Podman v4.9 release branch.

[NO NEW TESTS NEEDED]

Signed-off-by: tomsweeneyredhat <[email protected]>
@TomSweeneyRedHat TomSweeneyRedHat added the No New Tests Allow PR to proceed without adding regression tests label Oct 25, 2024
Copy link
Contributor

openshift-ci bot commented Oct 25, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: TomSweeneyRedHat

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Oct 25, 2024
@TomSweeneyRedHat
Copy link
Member Author

@mheon @lsm5 PTAL

@Luap99
Copy link
Member

Luap99 commented Oct 28, 2024

f39 EOL date is 2024-11-12, do we want/need to cut another release for this?

@Luap99
Copy link
Member

Luap99 commented Oct 28, 2024

Also CI seems broken, I remember fixing this issue on main but I would need to go through the git log to find it so I rather wait until someone tells me we a new release here

@lsm5
Copy link
Member

lsm5 commented Oct 28, 2024

f39 EOL date is 2024-11-12, do we want/need to cut another release for this?

Nobody's asked us yet. I would prefer not to cut a new release.

@TomSweeneyRedHat
Copy link
Member Author

I'll let @mheon decide on cutting a new release. If so, I'll chase down the build issues. If not, we can just close this.

@mheon
Copy link
Member

mheon commented Oct 29, 2024

We can PS about this tomorrow, but if the EOL is in two weeks it's probably not worth it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. No New Tests Allow PR to proceed without adding regression tests release-note-none
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants